http://delivery.acm.org/10.1145/2510000/2504778/p185-king.pdf?ip=152.1.11.208&id=250477... - 0 views
-
Jenny Darrow on 23 Apr 15Higher education conferences over the past few years have been full of presentations, papers and panels on the processes involved in migrating a campus and its people to Google Apps for Education. While it is useful to hear about marketing tchotchkes, data validation, and the pros and cons of web clients, what seems to get ignored is the process that led to the decision to move to Google Apps in the first place. At North Carolina State University, where students were already using Google Apps, the decision to move employees involved almost as much time, effort and heartache as the technical migration. As the users saw it, they had a working system, even if that system only worked because of huge expenditures of time and money both on the backend server maintenance and the client need to implement terribly complex workarounds for simple functionality. The end result: a 94-page white paper and the realization that it's hard to sell ice to Eskimos1 , even if you show them that their ice has already melted. This paper and presentation will discuss the information gathering and needs assessment done by NC State prior to the decision to move employees to Google Apps, and the successes and difficulties involved.